Handling dual priority applications in a wireless communication network

ABSTRACT

Embodiments of the present disclosure describe techniques for handling dual priority for a machine-to-machine device in a wireless communication network. The device may include computer-readable media having instructions and one or more processors coupled with the computer-readable media and configured to execute the instructions to configure, as a default configuration, the device with a first priority level for machine-type communications, receive a notification from an application associated with the device, the notification indicating that the application generated a communication to a network controller, the communication being associated with a second priority level that is higher than the first priority level, and in response to the notification, configure, as an override configuration, the device with the second priority level for machine-type communications. If a backoff timer is running for low priority application, and a current communication is not for a low priority, the communication is allowed to proceed.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application claims priority to U.S. Provisional PatentApplication No. 61/595,576, filed Feb. 6, 2012, entitled “AdvancedWireless Communication Systems and Techniques,” which is herebyincorporated by reference in its entirety for all purposes.

FIELD

Embodiments of the present disclosure generally relate to the field ofwireless communication systems, and more particularly, tomachine-to-machine communications in wireless communication networks.

BACKGROUND

Machine-to-machine (“M2M”) wireless machines or devices (hereafterreferred to as “M2M devices”) may communicate primarily or exclusivelywith other M2M devices, with little or no human intervention. Examplesof M2M devices may include wireless weather sensors, assembly linesensors, meters to track vehicles of a fleet, and so forth. In manycases these M2M devices may connect to a wireless network andcommunicate, e.g., over a wide area network such as the Internet, with anetwork server. M2M devices may be used with the IEEE 802.16 standard,IEEE Std. 802.16-2009, published May 29, 2009 (“WiMAX”), as well as inThird Generation Partnership Project (“3GPP”) networks. In parlance ofthe 3GPP Long Term Evolution (“LTE”) Release 10 (March 2011) (the “LTEStandard”), M2M communications may alternatively be referred to as“machine-type communications” (“MTC”). From a network perspective, M2Mcommunications may be considered to be relatively low-prioritycommunications due to their relatively high latency tolerances andinfrequent data transfers. However, most M2M devices that normallycommunicate on a low priority level may have rare occasions when theyneed to communicate on a priority level that is higher than a lowpriority.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detaileddescription in conjunction with the accompanying drawings. To facilitatethis description, like reference numerals designate like structuralelements. Embodiments are illustrated by way of example and not by wayof limitation in the figures of the accompanying drawings.

FIG. 1 illustrates an example wireless communication network inaccordance with some embodiments.

FIGS. 2 and 3 are block diagrams illustrating example communicationsbetween user equipment (mobile device) and a wireless communicationnetwork in accordance with some embodiments.

FIG. 4 is a process flow diagram for communications between a networkcontroller and user equipment in a wireless communication network inaccordance with some embodiments.

FIG. 5 is a process flow diagram for handling a dual priority by userequipment in a wireless network environment in accordance with someembodiments.

FIG. 6 is a process flow diagram for handling a dual priority by userequipment in a congested wireless network environment in accordance withsome embodiments.

FIG. 7 illustrates an example system that may be used to practicevarious embodiments described herein.

DETAILED DESCRIPTION

Embodiments of the present disclosure provide data techniques andconfigurations for handling dual-priority devices in a wirelesscommunication network. In the following detailed description, referenceis made to the accompanying drawings which form a part hereof, whereinlike numerals designate like parts throughout, and in which is shown byway of illustration embodiments in which the subject matter of thepresent disclosure may be practiced. It is to be understood that otherembodiments may be utilized and structural or logical changes may bemade without departing from the scope of the present disclosure.Therefore, the following detailed description is not to be taken in alimiting sense, and the scope of embodiments is defined by the appendedclaims and their equivalents.

Various operations are described as multiple discrete operations inturn, in a manner that is most helpful in understanding the claimedsubject matter. However, the order of description should not beconstrued as to imply that these operations are necessarily orderdependent. In particular, these operations may not be performed in theorder of presentation. Operations described may be performed in adifferent order than the described embodiment. Various additionaloperations may be performed and/or described operations may be omittedin additional embodiments.

The description may use the phrases “in an embodiment,” or “inembodiments,” which may each refer to one or more of the same ordifferent embodiments. Furthermore, the terms “comprising,” “including,”“having,” and the like, as used with respect to embodiments of thepresent disclosure, are synonymous.

As used herein, the term “module” may refer to, be part of, or includean Application-Specific Integrated Circuit (ASIC), an electroniccircuit, a processor (shared, dedicated, or group) and/or memory(shared, dedicated, or group) that execute one or more software orfirmware programs, a combinational logic circuit, and/or other suitablecomponents that provide the described functionality.

Example embodiments may be described herein in relation to wirelesscommunication networks including networks such as 3^(rd) GenerationPartnership Project (3GPP) Long Term Evolution (LTE) networks includingany amendments, updates, and/or revisions (e.g., LTE Release 10 (alsoreferred to as LTE-Advanced (LTE-A), LTE Release 11, etc.), WorldwideInteroperability for Microwave Access (WiMAX) networks, and the like.The embodiments described herein may operate in relation to a radioaccess network, e.g., an evolved Universal Terrestrial Radio AccessNetwork (E-UTRAN) having evolved node base stations (eNBs), and a corenetwork, e.g., an evolved packet core having gateways, managemententities, etc.

In other embodiments, communication schemes described herein may becompatible with additional/alternative communication standards,specifications, and/or protocols. For example, embodiments of thepresent disclosure may be applied to other types of wireless networkswhere similar advantages may be obtained. Such networks may include, butare not limited to, wireless local area networks (WLANs), wirelesspersonal area networks (WPANs) and/or wireless wide area networks(WWANs) such as cellular networks and the like.

The following embodiments may be used in a variety of applicationsincluding transmitters and receivers of a mobile wireless radio system.Radio systems specifically included within the scope of the embodimentsinclude, but are not limited to, network interface cards (NICs), networkadaptors, base stations, access points (APs), relay nodes, eNBs,gateways, bridges, hubs and satellite radiotelephones. Further, theradio systems within the scope of embodiments may include satellitesystems, personal communication systems (PCS), two-way radio systems,global positioning systems (GPS), two-way pagers, personal computers(PCs) and related peripherals, personal digital assistants (PDAs),personal computing accessories and all existing and future arisingsystems which may be related in nature and to which the principles ofthe embodiments could be suitably applied.

Techniques described herein provide for enabling user equipment (UE)such as an M2M device to provide at least two priority levels (e.g.,dual priority) for communications initiated by the UE in a wirelessnetwork environment. In some wireless communication environments, theM2M network overload control work may be simplified by restricting M2Mdevices to a single priority level for all applications executing on theM2M device. The device may be assigned a priority level of either “lowpriority” or “normal priority.” In practice, significant number ofmachine type communications may be categorized as “low priority” andhence the M2M devices may be assigned that setting.

However, most M2M devices that normally use “low priority” may also haveinfrequent, rare occasions when they need to use the “normal” prioritysetting. For example, electricity meters sending a daily report (e.g.,of the per hour usage) may send the report as “low priority.” However,there may be instances in which the electricity meter may want to sendan alarm with “normal priority,” for example, if the meter is beingtampered with or is being vandalized.

In another example, a road temperature sensor may send daily “I′m stillworking” communications with “low priority” but, if the road temperaturefalls to sub-zero, may need to immediately send a warning to the controlcenter with “normal priority.”

In yet another example, an M2M device may host multiple applications.For example, a room temperature application residing on an M2M devicemay require data transmission using “low priority,” while avideo-streaming application residing on the same device may require datatransmission using “normal priority.” The embodiments described hereinare not limited to the above examples; the above examples are includedfor illustration of the techniques described in the present disclosure.

If the device may only use either “low priority” or “normal priority”levels for communications, the need for a truly “low priority” device tosupport rare “normal priority” events may dissuade MTC customers fromusing the “low priority” setting for their M2M devices. Instead, the MTCcustomers may be encouraged to configure their devices for “normalpriority” level of communications at all times. This may haveundesirable consequences with respect to additional network overload.

Embodiments of the present invention provide applications that mayreside on an M2M device with the ability to override the device'sdefault “low priority” setting in cases when the applications may needto transmit a “normal priority” communication.

In one embodiment, the UE and/or communications initiated by the UE(e.g., requests initiated by the applications hosted by the UE) may beassigned a default (e.g., low) priority level. In some cases, forexample, in emergency and other situations described below in greaterdetail, the UE may be configured to override the default priorityassociated with the initiated request and assign a higher (e.g.,“normal”) priority level to the initiated request that may be treated bythe network according to the assigned priority level. For example, thenetwork may be congested and may not immediately accept a request orother communication from the UE that is associated with a defaultpriority (or lower level of priority), but may accept and process arequest or other communications from the UE that is associated with ahigher (normal) level that may be assigned to the communication by theUE. More specifically, if the network is determined to be congested andtherefore unable to process a request with a default (low) priority fromthe UE, the network may provide to the UE a wait time value, duringwhich the UE may refrain from attempting to contact the network withcommunications with low priority. However, if the UE initiates requestswith a higher (normal) priority level, these requests may be allowed tobe accepted by the network.

In another embodiment, it may be desired for the UE to have a capabilityto override access control configurations associated with the UE, suchas Extended Access Barring configuration. Extended Access Barring (EAB)is a mechanism for the operator(s) to control mobile originating accessattempts from UEs that are configured for EAB in order to preventoverload of the access network and/or the core network. In congestion oroverload situations, the operator may restrict access from UEsconfigured for EAB while permitting access from other UEs. UEsconfigured for EAB are considered more tolerant to access restrictionsthan other UEs. When an operator determines that it is appropriate toapply EAB, the network broadcasts necessary information to provide EABcontrol for UEs in a specific area.

However, in some instances, the Extended Access Barring configurationmay need to be overridden, typically in conjunction with low priorityoverride capability as described above. This may relate to the fact thattypically UEs configured for low access priority are also configured forEAB. Accordingly, when it is necessary to override low priority for acommunication initiated by a UE, it may also be necessary to override anEAB setting in order to allow the communication to proceed. Operationsof UEs configured to provide dual priority for communications initiatedby the UEs in different situations are described below in greaterdetail.

FIG. 1 schematically illustrates an example wireless network 100 inaccordance with some embodiments. The network 100 may include a RAN 20and a core network 25. In some embodiments, the network 100 may be anLTE network, the RAN 20 may be a E-UTRAN, and the core network 25 may bean Evolved Packet System (EPS) type core network. A UE 15 may access thecore network 25 via a radio link (“link”) with an eNB such as, forexample, one of eNBs 40, 42, etc., in the RAN 20. The UE 15 may be, forexample, a subscriber station (e.g., an M2M device) that is configuredto communicate with the eNBs 40, 42 in conformance with one or moreprotocols. The following description is provided for an example network100 that conforms with 3GPP for ease of discussion; however, subjectmatter of the present disclosure is not limited in this regard and thedescribed embodiments may apply to other networks that benefit from theprinciples described herein. In some embodiments, the UE 15 may beconfigured to communicate using a multiple-input and multiple-output(MIMO) communication scheme. One or more antennas of the UE 15 may beused to concurrently utilize radio resources of multiple respectivecomponent carriers (e.g., which may correspond with antennas of eNBs 40,42) of RAN 20. The UE 15 may be configured to communicate usingOrthogonal Frequency Division Multiple Access (OFDMA) in, e.g., downlinkcommunications, and/or Single-Carrier Frequency Division Multiple Access(SC-FDMA) in, e.g., uplink communications in some embodiments.

While FIG. 1 generally depicts the UE 15 as a mobile device (e.g., acellular phone), in various embodiments the UE 15 may be a personalcomputer (PC), a notebook, ultrabook, netbook, smartphone, an ultramobile PC (UMPC), a handheld mobile device, an universal integratedcircuit card (UICC), a personal digital assistant (PDA), a CustomerPremise Equipment (CPE), a tablet, or other consumer electronics such asMP3 players, digital cameras, and the like. As discussed above, the UE15 may be a Machine-Type Communication (MTC) device, also known as M2Mdevice. In the present disclosure, the terms “UE” and “device” will beused interchangeably for simplicity purposes. The eNBs 40, 42 mayinclude one or more antennas, one or more radio modules to modulateand/or demodulate signals transmitted or received on an air interface,and one or more digital modules to process signals transmitted andreceived on the air interface.

In some embodiments, communication with the UE 15 via RAN 20 may befacilitated via one or more nodes 45 (e.g., Radio Network Controllers).The one or more nodes 45 may act as an interface between the corenetwork 25 and the RAN 20. According to various embodiments, the one ormore nodes 45 may include a Mobile Management Entity (MME) that isconfigured to manage signaling exchanges (e.g., authentication of the UE15) between the base stations 40, 42 and the core network 25 (e.g., oneor more servers 50), a Packet Data Network Gateway (PGW) to provide agateway router to the Internet 65, and/or a Serving Gateway (SGW) tomanage user data tunnels or paths between the eNBs 40, 42 of the RAN 20and the PGW. Other types of nodes may be used in other embodiments.

The core network 25 may include logic (e.g., a module) to provideauthentication of the UE 15 or other actions associated withestablishment of a communication link to provide a connected state ofthe UE 15 with the network 100. For example, the core network 25 mayinclude one or more servers 50 that may be communicatively coupled tothe base stations 40, 42. In an embodiment, the one or more servers 50may include a Home Subscriber Server (HSS), which may be used to manageuser parameters such as a user's International Mobile SubscriberIdentity (IMSI), authentication information, and the like. The corenetwork 25 may include other servers, interfaces, and modules. In someembodiments, logic associated with different functionalities of the oneor more servers 50 may be combined to reduce a number of servers,including, for example, being combined in a single machine or module.

According to various embodiments, the network 100 may be an InternetProtocol (IP) based network. For example, the core network 25 may be, atleast in part, an IP based network, such as a packet switched (PS)network. Interfaces between network nodes (e.g., the one or more nodes45) may be based on IP, including a backhaul connection to the basestations 40, 42. In some embodiments, the network 100 may be enabled toprovide connection with a circuit switched (CS) network (e.g., CSdomain). In an embodiment, a UE 15 may communicate with the network 100according to one or more communication protocols, such as, for example,Radio Resource Control (RRC) protocol adapted for LTE communicationenvironment.

An example connection diagram between the UE 15 and the network 100 isillustrated in FIG. 2. As the diagram 200 illustrates, the UE 15 maysend an RRC connection request message 204 to a network controller 206.The RRC connection request message 204 may be a request by the UE 15 forallocation of radio resources so that the UE 15 may exchange data withthe RAN 20. The network controller 206 may control establishment and/ormaintenance of RRC connections between the UE 15 and the RAN 20. Thenetwork controller 206 may be disposed in an eNB 40 or 42 with which theUE 15 attempts to establish an RRC connection. In other embodiments, thenetwork controller 206, or components thereof, may be disposed inadditional/alternative network entities, e.g., within a node of the oneor more nodes 45, a server of the one or more servers 50, etc.

If the RAN 20 is congested and is not be able to support an RRCconnection associated with the RRC connection request message 204, thenetwork controller 206 may respond with an RRC connection reject message208 to reject the RRC connection request message 204. In this case anRRC connection between the UE 15 and the RAN 20 may not be established.In one example, an RRC connection request message may relate to a NASrequest message, such as attach request, tracking area update request,or extended service request.

In some instances, for particular types of devices, such as MTC devices,the network controller 206 may provide, in the connection reject message208, a wait time (WT) value also known as extended wait time or EWTAtimer associated with the device (known as a “backoff timer”) may startrunning for the duration of the wait time and may keep the device “onhold,” e.g., refraining from sending communications to the network,until the wait time expires and the device may be allowed to resend therequest to the network.

A wait time value may be provided to the device (UE) in other instances.FIG. 3 is a block diagram 300 illustrating an instance where the UE 15may initiate a connection request by sending an RRC connection requestmessage 304 to the network controller 206. The network controller 206 inthis instance may determine that the RAN 20 may be able to support anRRC connection associated with the RRC connection request message 304.Accordingly, the network controller 206 may respond with a connectionsetup message 308. A number of other handshake messages (not shown) maybe transmitted between the UE 15 and the network controller 206 inaccordance with an adapted communication protocol. For example, the UE15 may respond to the connection setup message 308 with a notificationthat a connection setup is complete; the network controller 206 mayissue a security mode establishment command; the UE 15 may notify thenetwork controller 206 that the security mode has been established. Inone embodiment, the network controller 206 may provide an RRC connectionrelease message 310 that may include a wait time value. In summary, whenthe network is congested or overloaded, the network controller 206 mayspecify an extended wait time and ask the UE 15 to “back off” for theduration of the wait time. The foregoing describes how a UE 15configured for dual priority may handle the situations when the networkis congested and the UE 15 receives the wait time value from the networkin response to a request (e.g., a connection request).

FIG. 4 is a process flow diagram illustrating communications between anetwork controller, e.g., network controller 206, and a UE, e.g., UE 15,in a wireless network environment in accordance with an embodiment. Itis assumed that the UE is configured as a dual-priority device. Forexample, the UE may be configured to provide an ability to override, insome cases, low priority associated with the device or with one or moreapplications residing on the device. (It should be understood that “dualpriority” in the context of this disclosure may mean two or morepriorities. The example with two priorities is provided merely forillustrative purposes.)

The process 400 begins at block 402, where the UE may send a request(e.g., connection request) to the network controller. As discussedabove, there may be different types of communications initiated by themobile device, such as, for example, an RRC Connection Request. Asdescribed above in reference to FIG. 2, if the network is congestedabove a certain determined level that allows establishing a connectionwith the device the network controller may respond with a rejectionmessage (e.g., the network controller may send the RRC Connection Rejectmessage described above) along with a wait time value, as illustrated byblock 404. At block 408, the received wait time may be used to start abackoff timer that determines the time period within which the devicemay refrain from sending another request to the network controller. Atblock 410, a priority value (e.g., default (low) priority or normalpriority) associated with the device's request may be stored by thedevice for future use.

FIG. 5 is a process flow diagram for handling dual-prioritycommunications by user equipment, e.g., UE 15, in a wireless networkenvironment in accordance with some embodiments. The process 500 beginsat block 502, where a UE may receive a configuration providing anability to override a default (e.g., low) priority associated with theUE and/or applications residing on the UE. For example, a newconfiguration parameter may be added to the UE configuration that mayoverride the default priority. More specifically, a new configurationparameter may be added to the non-access stratum (NAS) configuration ofthe UE that allows for overriding of the NAS low priority indicatorsetting. In another example, a new configuration parameter may be addedto the non-access stratum configuration that allows for overriding anExtended Access Barring configuration, as discussed above. Theconfiguration parameter may be provided by a provider of a wirelesscommunication network in which the UE is operating. As described above,the wireless communication network may comprise UTRAN or E-UTRAN, forexample.

At block 504, a communication, such as a request message to a networkcontroller, e.g., network controller 206, may be initiated by the UE.For example, an application residing on the UE may indicate a need tosend a request to the network controller. As discussed above, a requestto the network controller may be any type of request, such as RRCConnection Request. In other examples, a UE may initiate a request tothe network controller in connection with an attach procedure (e.g.,request to “attach” the UE to the network), tracking area updateprocedure, location updating procedure, routing area update procedure,service request procedure, and the like. In yet another example, anapplication may initiate a request (e.g., request to send information toan end user via the network).

At decision block 506 it may be determined whether an applicationinitiating a communication is associated with a priority level that isdifferent than a default priority. For example, it may be determinedwhether an application is associated with a normal priority. If it isdetermined that the application initiating the communication is notassociated with a priority other than a default priority, the process500 moves to decision block 508. Otherwise, the process 500 moves toblock 512.

At decision block 508 it may be determined whether a communication fromthe application requires overriding the default priority. As discussedabove, some applications that typically are associated with, and sendrequests or other communications associated with, default (low)priority, occasionally may need to send communications associated withhigher priority. For example, an electricity meter may want to send analarm with “normal priority,” for example, if the meter is beingtampered with or is being vandalized, as opposed to a daily report thatis typically sent with a low priority.

If it is determined that the communication does not require overriding adefault priority, at block 510 the communication is initiated (e.g.,sent) to the controller with a default priority indication and istreated by the network controller according to an indicated priority.

If it is determined that the communication requires overriding a default(e.g., low) priority, the process 500 moves to block 512, where the lowpriority is overridden, for example, using the configuration setting asdescribed in reference to block 502. At block 514, a communication isinitiated (e.g., sent) to the controller with a different level ofpriority which is allowed by the dual priority character of the UEconfiguration (e.g., normal priority).

FIG. 6 is a process flow diagram for handling dual-prioritycommunications by user equipment in a congested wireless networkenvironment in accordance with some embodiments. As described above inreference to FIG. 4, in case of a congested network, the networkcontroller may respond to a communication (e.g., request to connect)from UE with a rejection message that may include a wait time valuedirecting the UE to refrain from sending communications to the networkuntil the wait time expires. The UE may start a backoff timer with thereceived wait time value and store the priority value associated withthe UE earlier communication that triggered the rejection from thenetwork.

In some situations, the received wait time value may be ignored by theUE. However, for the purpose of an embodiment illustrated in FIG. 6 itis assumed that the UE may not ignore the received wait time value.

The process 600 begins at block 602, where the UE may be configured witha configuration providing an ability to override a default (e.g., low)priority associated with the UE and/or applications residing on the UE,similar to the example described above in reference to FIG. 5. At block604, a communication to a network controller may be initiated by the UE.As described in reference to FIG. 5, a communication may relate toconnection (e.g., a PDN connection) or other Mobility Managementfunctions (e.g., attach procedure, tracking area update procedure,location updating procedure, routing area update procedure, servicerequest procedure, and the like). At decision block 606 it may bedetermined whether a backoff timer associated with UE is running If itis determined that a backoff timer is not running, the process moves toblock 614, where the initiated communication may be sent to the networkcontroller.

If it is determined that the backoff timer is running, at decision block608 it may be determined whether the backoff timer was started as aresult of a prior communication (e.g., a response to a communicationsent by the UE) that is associated with a default (e.g., low) priority.For example, the backoff timer may have been started due to priorMobility Management functions, for example, NAS request messages such asattach request, tracking area update request, or extended servicerequest. As described in reference to FIG. 4 (block 410), when thebackoff timer starts, the priority value (low or normal) associated withthe communication that triggers the backoff timer may be stored.Accordingly, a priority level of a communication that triggered thebackoff timer may be determined at decision block 608. If it isdetermined that the backoff timer was started in connection with acommunication having a priority level other than default (e.g., normalpriority), the process 600 moves to block 616, where the initiatedcommunication may be sent only upon an expiration of the backoff timer.

If it is determined that the backoff timer was started in connectionwith a prior communication having a low priority level (e.g., a priorNAS request message having a low priority level), at decision block 610it may be determined whether the initiated communication is associatedwith a priority other than a default priority, e.g., normal priority.Some instances of requests that may be associated with a normal priorityare described above in reference to FIG. 5 (block 508). If it isdetermined that the initiated communication is not associated with apriority other than a default (low) priority, the process 600 moves toblock 616, where the initiated communication may be sent only upon anexpiration of the backoff timer. If it is determined that the initiatedcommunication is associated with a priority other than a default (low)priority, at block 612 the UE default (low) priority may be overridden.At block 614, the initiated communication may be sent with a priorityother than default, e.g., normal priority, which is higher than thedefault low priority.

Embodiments of the present disclosure may be implemented into a systemusing any suitable hardware and/or software to configure as desired.FIG. 7 schematically illustrates an example system that may be used topractice various embodiments described herein. FIG. 7 illustrates, forone embodiment, an example system 700 having one or more processor(s)704, system control module 708 coupled to at least one of theprocessor(s) 704, system memory 712 coupled to system control module708, non-volatile memory (NVM)/storage 717 coupled to system controlmodule 708, and one or more communications interface(s) 720 coupled tosystem control module 708.

In some embodiments, the system 700 may be capable of functioning as theUE 15 as described herein. In other embodiments, the system 700 may becapable of functioning as the one or more nodes 45 or one or moreservers 50 of FIG. 1 or otherwise provide logic/module that performsfunctions as described for eNB 40, 42 and/or other modules describedherein. In some embodiments, the system 700 may include one or morecomputer-readable media (e.g., system memory or NVM/storage 717) havinginstructions and one or more processors (e.g., processor(s) 704) coupledwith the one or more computer-readable media and configured to executethe instructions to implement a module to perform actions describedherein.

System control module 708 for one embodiment may include any suitableinterface controllers to provide for any suitable interface to at leastone of the processor(s) 704 and/or to any suitable device or componentin communication with system control module 708.

System control module 708 may include memory controller module 710 toprovide an interface to system memory 712. The memory controller module710 may be a hardware module, a software module, and/or a firmwaremodule.

System memory 712 may be used to load and store data and/orinstructions, for example, for system 700. System memory 712 for oneembodiment may include any suitable volatile memory, such as suitableDRAM, for example. In some embodiments, the system memory 712 mayinclude double data rate type four synchronous dynamic random-accessmemory (DDR4 SDRAM).

System control module 708 for one embodiment may include one or moreinput/output (I/O) controller(s) to provide an interface to NVM/storage717 and communications interface(s) 720.

The NVM/storage 717 may be used to store data and/or instructions, forexample. NVM/storage 717 may include any suitable non-volatile memory,such as flash memory, for example, and/or may include any suitablenon-volatile storage device(s), such as one or more hard disk drive(s)(HDD(s)), one or more compact disc (CD) drive(s), and/or one or moredigital versatile disc (DVD) drive(s), for example.

The NVM/storage 717 may include a storage resource physically part of adevice on which the system 700 is installed or it may be accessible by,but not necessarily a part of, the device. For example, the NVM/storage717 may be accessed over a network via the communications interface(s)720.

Communications interface(s) 720 may provide an interface for system 700to communicate over one or more network(s) and/or with any othersuitable device. The system 700 may wirelessly communicate with the oneor more components of the wireless network in accordance with any of oneor more wireless network standards and/or protocols.

For one embodiment, at least one of the processor(s) 704 may be packagedtogether with logic for one or more controller(s) of system controlmodule 708, e.g., memory controller module 710. For one embodiment, atleast one of the processor(s) 704 may be packaged together with logicfor one or more controllers of system control module 708 to form aSystem in Package (SiP). For one embodiment, at least one of theprocessor(s) 704 may be integrated on the same die with logic for one ormore controller(s) of system control module 708. For one embodiment, atleast one of the processor(s) 704 may be integrated on the same die withlogic for one or more controller(s) of system control module 708 to forma System on Chip (SoC).

In various embodiments, the system 700 may be, but is not limited to, aserver, a workstation, a desktop computing device, or a mobile computingdevice (e.g., a laptop computing device, a handheld computing device, atablet, a netbook, etc.). In various embodiments, the system 700 mayhave more or less components, and/or different architectures. Forexample, in some embodiments, the system 700 may include one or more ofa camera, a keyboard, liquid crystal display (LCD) screen (includingtouch screen displays), non-volatile memory port, multiple antennas,graphics chip, application-specific integrated circuit (ASIC), andspeakers.

According to various embodiments, the present disclosure describes adevice, comprising one or more computer-readable media havinginstructions; and one or more processors coupled with the one or morecomputer-readable media and configured to execute the instructions toconfigure, as a default configuration, the device with a first prioritylevel for machine-type communications; receive a notification from anapplication associated with the device, the notification indicating thatthe application generated a communication to a network controller, thecommunication being associated with a second priority level that ishigher than the first priority level; and in response to thenotification, configure, as an override configuration, the device withthe second priority level for machine-type communications.

According to various embodiments, the present disclosure describes asystem comprising a network controller having a controller processor anda controller memory having instructions stored thereon that, whenexecuted on the controller processor, cause the controller processor toprovide a wait time value in response to a first communication to thenetwork controller. The system further includes a device configured witha first priority level for machine-type communications, the devicehaving a device processor and a device memory having instructions storedthereon that, when executed on the device processor, cause the deviceprocessor to generate a second communication to the network controller;determine whether a backoff timer associated with the firstcommunication is running; and based on the determination, determinewhether to send the second communication to the network controller.

According to various embodiments, the present disclosure describes acomputer-implemented method comprising enabling a dual priorityconfiguration, the enabling including a default configuration with afirst priority level and an ability to override the first priority leveland assign a second priority level, the second priority level beinghigher than the first priority level; receiving an indication of acommunication to be sent to a network controller, the communicationbeing associated with the second priority level; and sending thecommunication with the second priority level to the network controller.

According to various embodiments, the present disclosure describes acomputer-readable storage medium having instructions stored thereonthat, when executed on a computing device, cause the computing device toconfigure a wireless device with a dual priority configuration, theconfiguring including assigning a default configuration associated witha first priority level and providing an ability to override the firstpriority level and assign a second priority level, the second prioritylevel being higher than the first priority level; receive an indicationof a communication to be sent to a network controller, the communicationbeing associated with the second priority level; determine whether abackoff timer associated with an earlier communication is running;determine whether the earlier communication is associated with the firstpriority level; and send the communication when it is determined thatthe backoff timer is running and the earlier communication is associatedwith the first priority level.

Although certain embodiments have been illustrated and described hereinfor purposes of description, a wide variety of alternate and/orequivalent embodiments or implementations calculated to achieve the samepurposes may be substituted for the embodiments shown and describedwithout departing from the scope of the present disclosure. Thisapplication is intended to cover any adaptations or variations of theembodiments discussed herein. Therefore, it is manifestly intended thatembodiments described herein be limited only by the claims and theequivalents thereof.

1.-30. (canceled)
 31. One or more computer-readable media havinginstructions that, when executed, cause a device to: receive, from upperlayers, a request that a user equipment (UE) access a wirelesscommunication network for services associated with a first prioritylevel; determine a backoff timer is running; and determine a timing oftransmission of a non-access stratum (NAS) request message to a networkcontroller based on a determination of whether the backoff timer wasinitiated based on another NAS request message communication having thefirst priority level or a second priority level that is lower than thefirst priority level.
 32. The one or more computer-readable media ofclaim 31, wherein the instructions, when executed, further cause thedevice to: determine that the backoff timer was initiated based onanother NAS request message having the first priority level; andtransmit the NAS request message upon expiration of the backoff timer.33. The one or more computer-readable media of claim 31, wherein theinstructions, when executed, further cause the device to: determine thatthe backoff timer was initiated based on another NAS request messagehaving the second priority level; and transmit the NAS request messagewhile the backoff timer is running.
 34. The one or morecomputer-readable media of claim 31, wherein the other NAS requestmessage has an indicator to indicate the first or second priority level.35. The one or more computer-readable media of claim 34, wherein theother NAS request message is an attach request, a tracking area updaterequest, or an extended service request.
 36. The one or morecomputer-readable media of claim 31, wherein the NAS request message isan attach request, a tracking area update request, or an extendedservice request.
 37. The one or more computer-readable media of claim31, wherein the instructions, when executed, further cause the deviceto: add a configuration parameter associated with a device configurationmanagement object, the configuration parameter to indicate an ability ofthe device to override a configuration of the device, wherein theconfiguration is a default configuration associated with the secondpriority level or an extended access barring (EAB) configuration. 38.The one or more computer-readable media of claim 37, wherein theconfiguration parameter is provided to the management object by aprovider of the wireless communication network.
 39. The one or morecomputer-readable media of claim 31, wherein the UE is amachine-to-machine device.
 40. The one or more computer-readable mediaof claim 31, wherein the instructions, when executed, further cause thedevice to: configure the device with a dual-priority configuration byassigning a default configuration associated with the second prioritylevel and providing an ability to override the second priority level andassign the first priority level.
 41. An apparatus comprising the one ormore computer-readable media of claim 31 and further comprising: one ormore processors coupled with the one or more computer-readable media andconfigured to execute the instructions.
 42. The apparatus of claim 41,wherein the apparatus is a machine-to-machine device.
 43. The apparatusof claim 42, wherein the network controller is a machine-typecommunication (MTC) controller.
 44. An apparatus comprising: logic toconfigure, as a default configuration, the apparatus with a firstpriority level for machine-type communications over a wirelesscommunication network; logic to receive a notification from anapplication associated with the apparatus, the notification indicatingthat the application is associated with a second priority level that ishigher than the first priority level; and logic to, in response to thenotification, configure, as an override configuration, the apparatuswith the second priority level for machine-type communications.
 45. Theapparatus of claim 44, further comprising: logic to determine whether abackoff timer associated with an earlier communication is running. 46.The apparatus of claim 45, further comprising: logic to determinewhether the earlier communication is associated with the first prioritylevel; and logic to initiate a communication to a network controller inan event it is determined that the earlier communication is associatedwith the first priority level.
 47. The apparatus of claim 46, furthercomprising: logic to initiate the communication to the networkcontroller after the backoff timer expires in an event it is determinedthat the earlier communication is not associated with the first prioritylevel, wherein the earlier communication is determined to be associatedwith the second priority level.
 48. The apparatus of claim 46, whereinthe communication to the network controller comprises a radio resourcecontrol (RRC) attach request, an RRC tracking area update request, anRRC service request, an RRC location request, or an RRC routing areaupdate request.
 49. The apparatus of claim 46, wherein the networkcontroller is part of an evolved universal terrestrial radio accessnetwork (E-UTRAN).
 50. The apparatus of claim 44, further comprising:logic to add a configuration parameter associated with a deviceconfiguration management object, the configuration parameter indicatingan ability to override the default configuration associated with theapparatus.
 51. The apparatus of claim 50, wherein the configurationparameter is provided to the management object by a provider of thewireless communication network.
 52. The apparatus of claim 44, whereinthe apparatus is a machine-to-machine device.
 53. One or morecomputer-readable media having instructions that, when executed, cause anetwork controller to: configure a machine-to-machine (M2M) device witha dual-priority configuration in which the M2M device is able tooverride a default, low-priority configuration or an extended accessbarring configuration; and receive one or more network requests from theM2M device, wherein individual network requests of the one or morenetwork requests include priority indicators associated with respectivenetwork requests.
 54. The one or more computer-readable media of claim53, wherein the instructions, when executed, are to cause the networkcontroller to: provide, to a device configuration management object ofthe M2M device, a configuration parameter to indicate the ability of theM2M device to override the default, low-priority configuration or theextended access barring configuration.
 55. An apparatus, comprising: theone or more computer-readable media of claim 53; and one or moreprocessors coupled with the one or more computer readable media andconfigured to execute the instructions.
 56. The apparatus of claim 55,further comprising the network controller, wherein the networkcontroller is a machine-type communication (MTC) controller.
 57. Acomputer-implemented method comprising: under control of one or morecomputing devices configured with executable instructions, enabling adual priority non-access stratum (NAS) configuration, the enablingincluding a default configuration with a first priority level and anability to override the first priority level and assign a secondpriority level, the second priority level being higher than the firstpriority level; receiving, from upper layers, a request for servicesassociated with the second priority level; and sending a communicationwith the second priority level to a network controller.
 58. The methodof claim 57, wherein the sending the communication with the secondpriority level to the network controller includes: determining whether abackoff timer associated with an earlier communication is running;determining whether the earlier communication is associated with thefirst priority level; and sending the communication when it isdetermined that the backoff timer is running and the earliercommunication is associated with the first priority level.
 59. Themethod of claim 57, further comprising: sending the communication afterthe backoff timer expires when it is determined that the backoff timeris running and the earlier communication is not associated with thefirst priority level.